Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'cache-hit' as output #327

Merged
merged 1 commit into from
Sep 24, 2021
Merged

Conversation

WtfJoke
Copy link
Contributor

@WtfJoke WtfJoke commented Sep 3, 2021

Note to maintainers: I'm not sure about the changes in module.exports they came from the formatting task afaik. If you want I can revert these lines.

@WtfJoke WtfJoke marked this pull request as ready for review September 3, 2021 19:10
@WtfJoke WtfJoke mentioned this pull request Sep 3, 2021
Copy link

@hectorgrecco hectorgrecco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@MikkelHornJP
Copy link

looking forward to getting this merged :-)

@WtfJoke
Copy link
Contributor Author

WtfJoke commented Sep 13, 2021

@dmitry-shibanov I usually dont like to ping people, but is this something you can review? 🙂

@therynamo
Copy link

therynamo commented Sep 14, 2021

Would love this feature! 😄 Really looking forward to it.

I was just following this blog https://avraam.dev/posts/reducing-github-action-time and was going to use that feature with this action - but I see it is not supported yet

@julada
Copy link

julada commented Sep 22, 2021

Could you please review these simple changes @MaksimZhukov?

@dmitry-shibanov
Copy link
Contributor

Hello everyone. Sorry for the late reply.
@WtfJoke, Could you please run the npm ci && npm run build command with npm 6.x.

@WtfJoke
Copy link
Contributor Author

WtfJoke commented Sep 23, 2021

@WtfJoke, Could you please run the npm ci && npm run build command with npm 6.x.

That was it thanks! I rebased and force pushed the changes :) Feel free to review it now @dmitry-shibanov

@MaksimZhukov MaksimZhukov merged commit 270253e into actions:main Sep 24, 2021
@MaksimZhukov
Copy link
Contributor

Hello @WtfJoke! Thank you for the contribution and sorry for the inconvenience!
We will release a new action version early next week.

@WtfJoke
Copy link
Contributor Author

WtfJoke commented Sep 24, 2021

No worries :) Thanks for merging.
Glad I could contribute something

Copy link

@358jackchong 358jackchong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chong

deining pushed a commit to deining/setup-node that referenced this pull request Nov 9, 2023
I would have opened a pull request, but for some reason GitHub was
preventing me to do so...
Anyway, here's the description:

This PR makes the action run on whatever has been checked out by
previous steps.
This is better because it makes the action faster and solves some issues
that are caused by it pulling from the wrong ref (especially in PRs that
involve a fork).

The previous branch-related inputs have been removed, in favor of a new
input called `new-branch`: this will allow you to create a new branch
from the starting ref. If the branch already exists the action will try
to push anyway, but that can result in the remote rejecting the push
because it's not straightforward. For info on how to handle this
situation, please check out the README.

In conclusion, this PR makes the user responsible for handling branches,
while still keeping an easy-to-use option to create new branches for
those who need it: just make sure that you also consider when the branch
already exists.

Fixes actions#327
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support cache-hit state
9 participants